Robert's File Transfer (RFT) is a simple, console based, program I wrote to facilitate UUCP file transfers between systems. To use it you need UUPC 3.1 for Macintosh and a UUCP account. To use this, you must have enough experience on a Macintosh to configure UUPC, and you must maintain a good relationship with your host's administrator. :-)
There is nothing fancy about RFT. A simple command line interface does everything, and the necessary files are spooled to your SPOOLDIR.
The RFT application must be located in the same folder as your "UUPC Settings" file. Alternately, you may place a copy of your UUPC settings file into RFT's folder.
You have three choices at the RFT menu. You can send a file, request a file, or quit. Typing the quoted letter will give you the following options:
This will generate 2 files in your SPOOLDIR, named C.* and D.* file. The C.* file is the command file; a TEXT file that has the necessary information for UUPC to perform its function. The D.* file is a copy of the file you want to send.
RFT will only copy the data fork of the file. Therefore, you must, at least, BinHex of MacBinarize your files in order to have them correctly copy to the remote system. RFT doesn't do it for you.
First, you must select the file you want to send. You can specify the name with regard to your PUBDIR, using a UNIX style path name (e.g. "~/myfile"), or, you can type the full path name of the file using a Mac or a UNIX style pathname. (E.g. "My HD:my folder:my file" or "My HD/my folder/my file".)
RFT will change any occurances of “/” to “:”. As this may cause some problems with Mac files names which already have “/”s in their names, you can also use the Mac's StandardGetFile dialog to grab the file name for you. To do this, simply type a "*" at the prompt.
Next, you must provide the name of the remote system. This name must be in the MAILSERVICE or in the ROUTEVIA 'STR 's of you "UUPC" Settings file.
Then, you type the name your file will be saved as on the remote system. As the file permissions on the remote system can be an obstruction to successful file copying, any name that doesn't begin with “~/” (the remote PUBDIR), will prompt a warning asking you if you really want to continue.
Last, if you want the remote system to notify a user that a file has just been copied, you can enter the recipient’s user name. RFT will put it in your C.* file with the necessary option.
Easy! But, the file request is easier. :-)
In this case, RFT will generate only a C.* file.
First, type the remote system name. Again, it must be in your MAILSERVICE or ROUTEVIA 'STR 's.
Next, type the name of the file you want. Again, as any file transfer from anywhere other than the remote PUBDIR may cause problems, you will be given the choice of exiting if you don't start the name with "~/".
Finally, type the local file name you want for the requested file. Here, as I can't predict the behaviour of UUPC if you don't put it in your PUBDIR, the file name must start with "~/" (meaning PUBDIR). The RFT command will exit if another location is specified.
In the current version, RFT can only send or request files to or from an immediate neighbour. A file path like: "mainnode!subnode!~/file" can't be processed.
File requests with file names containing spaces or any meta-characters can lead to confusion and should be avoided.
RFT is a small program. Don't expect too much of it.
UUCP has interesting possibilities concerning file transfers. However, it far from being a friendly way to transfer a file. For instance, I don't know of any way to “scan” a remote system to know what they have available.
Also, as stated before, file permissions at your neighbour sites might limit what files you can access. Usually, a "public" file within a non-public directory can't be access via uucp. All the names in the path name must offer the right access for uucp to complete its task.
RFT has nothing in common with the usual Macintosh user interface. It uses a command line interface, as provided by Think C’s built-in console. The size of the application is less than 30k, and it requires 385k of RAM. (It can probably run with less than that but as everybody today certainly has at least 4 megs...). Even if RFT is a useful tool for UUPC, I don't think that a more sophisticated interface will be really useful.
You may make and give away verbatim copies of this package without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers, and include an unmodified copy of this document.
Robert's File Transfer (RFT), must remain Freely Available. You may charge a reasonable copying fee for any distribution of this package. You may not charge a fee for this package itself, or for support of this package. However, you may distribute this package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this package as a product of your own.
The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS PACKAGE IS PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE COPYRIGHT HOLDER SHALL NOT BE HELD LIABLE FOR ANY DAMAGES WHATSOEVER ARISING FROM THE USE OF, MIS-USE OF, OR INABILITY TO USE THIS PACKAGE.
I am interested in knowing who uses RFT. Please drop me a line if you use it, or send me a post card from your home town. If you want, I will e-mail you notices of changes as new versions become available.
If you want any particular feature to be added to RFT, feel free to ask. I will do my best to meet your needs.
You can send mail or e-mail to:
Robert Pellerin
6270, bd Léger, app. 3
Montréal-Nord, Qc H1G 1L3
Canada
Internet: robert@RP.CAM.ORG
I am currently running a small Mac BBS at (514) 328-4726. If you are from the Montreal area and can handle a French interface, feel free to give us a call.
